-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate remote cache server for Bazel #21
base: main
Are you sure you want to change the base?
Conversation
Is the |
@chickenandpork It's included intentionally, so I could test the branch in GHA directly. This however is not intended to be used directly as it's not really working stable. Are you interested in taking over and finishing this PR? |
OK, I understand; it looked like an error of duplicate code!
I don't think my javascript is sufficient. I only worked javascript (and coffeescript!) briefly around 2020. Sorry :( Personally I use a local buchgr cache and I set up the same in ephemeral build clusters. |
I'm interested in picking this up. What's not stable? What else is outstanding? |
@JohnAmican The summary is in #18 (comment), the stability is the main issue as on large projects the REST API calls to the GHA cache get rate limited. |
Related to #18
This pull request introduces a significant enhancement to the setup-bazel action by implementing a remote cache server for Bazel build outputs, aiming to improve build performance and cache utilization.
remote-cache-server.js
that creates an HTTP server compatible with Bazel's remote caching API. This server handlesGET
andPUT
requests to store and retrieve cache objects, leveraging@actions/cache
for underlying storage.index.js
to start the remote cache server as a detached process during the action's execution. The server's URL is then added to.bazelrc
to enable Bazel to use it for caching.config.js
to include settings for the remote cache server's URL and log file path, ensuring that these new features are configurable.post.js
to stop the remote cache server gracefully at the end of the action's execution and logs the server's output for debugging purposes.package.json
to include the remote cache server in the build process, ensuring that all necessary components are compiled and ready for use.For more details, open the Copilot Workspace session.